Updating Firmware

The Avaya IP Telephone File Server Application server can act in one of 4 modes:

• As an TFTP/FTP/HTTP/HTTPS server, called the basic Avaya IP Telephone File Server Application server to support the IP telephones.

NOTE: TFTP and FTP servers apply only to 4600 Series IP Telephones.

• As a basic Avaya IP Telephone File Server Application server plus as a client to pass data to a central fileserver.
• As a basic Avaya IP Telephone File Server Application server.
• As both file server and client server.

These various options can be selected within the configuration tools provided.

With the exception of the basic mode, the IP Telephone File Server Application software acts as either the client or server to provide simple file server firmware download. The IP Telephone File Server Application uses the HTTPS server for secure transmission using TLS.

NOTE: The IP Telephone File Server Application uses RSA, AES256 and SHA security standards as defaults.

Acting as a client, the IP Telephone File Server Application server requests firmware updates from a central file server. When set as the client and optioned for firmware updates, the IP Telephone File Server Application sever periodically requests a list of any new firmware from the primary/secondary file server, in that order.

A list of all available firmware or other files stored in the file server Updates directory is delivered to the IP Telephone File Server Application server acting as a client. The file server application checks the files in its own Updates directory and requests all files it does not have using HTTPS GET requests.

On successfully receiving new files, the server unzips them and places copies in each of the TFTPdata (46xx only), HTTPdata, and HTTPSdata subdirectories. The new files are then available for telephone download.

To use this feature, assign the following configuration items:

1. Choose the mode for each IP Telephone File Server Application server (client or file server).
2. Enable the Firmware distribution option in the INI setting.
3. Assign a primary and optional secondary file server address in each IP Telephone File Server Application client to look for new data.
4. Select the frequency of update. The default is “hourly.”

To check the backup operation, place a file in the Updates subdirectory of the file server. Verify that it is received and stored in the Updates directory of the IP Telephone File Server Application basic server. Ensure that zipped files have also been unzipped.

NOTE: If you have both Linux and Windows file servers, it might be easier to ZIP file telephone archives only. Each format can, however, be unpacked in the local IP Telephone File Server Application server.

NOTE: HTTPS proxy support is built in, which allows broader use over an extranet or the Internet. This mode is currently untested.